System and Method of RFID Portals

ABSTRACT

An RFID portal is provided for placing at an access point associated with a temporary event. The access point is controlled by a security control. The portal has a portal body erectable on at least one side of a user pathway at the access point; and an RFID reader in the portal body for reading an RFID tag issued to, and worn by, an individual user for the event that has an encoded unique UserID readable by the RFID reader. The RFID reader is located in the portal body, so as to be physically proximate to a location of the user&#39;s body where the RFID tag is worn. The RFID reader is in communication with a server which has stored a list of valid UserIDs for the event. The RFID portal also has an indicator system for receiving notification from the server that the read UserID is a valid UserID for the event and generating an indication to the security control, such that the security control permits the user to proceed along the pathway.

CROSS-REFERENCE TO THE RELATED APPLICATION

This application claims priority to U.S. Provisional Application Ser.No. 62/366,150, filed on Jul. 25, 2016, the contents of which are herebyincorporated by reference in its entirety.

FIELD OF INVENTION

The field of invention relates to venue control and in particularrelates to access controls to manage the entrances and exits of venuesfor temporary events such as festivals and fairs.

BACKGROUND

Festivals and fairs especially busy ones tend to have long line ups atentrances and exits as it takes time to process visitors and to validatetheir tickets or other entrance credentials. Thus visitors are requiredto wait, rain or shine, and waste valuable time that could have beenspent actually enjoying the event.

The festival industry is booming and is providing a fertile ground forvendors to showcase and offer sampling opportunities to their customerbase. Such temporary events are proving to be attractive marketingcampaigns for vendors looking to increase their customer base andintroduce new consumers to their products by offering an opportunity tosample various items.

A festival is an event ordinarily staged by a community, centering onand celebrating some unique aspect of that community and its traditions,often marked as a local or national holiday. Festivals often serve tomeet specific purposes, especially in regard to commemoration and/orcelebration. A festival provides an opportunity for people to cometogether and celebrate while also partaking in entertainment.

A food festival is an event celebrating food or drink. A food festivalusually highlights the output of producers from a certain region. Somefood festivals are focused on a particular type of food item. There arealso specific beverage festivals, such as the famous Oktoberfest inGermany for beer. Many cities hold festivals to celebrate wine or otherproduce from local producers.

A fair is a gathering of people to display or trade produce or othergoods, to parade or display animals and often to enjoy associatedentertainment like a circus or midway attractions. Festivals and fairsare normally temporary in nature; some last only an afternoon whileothers may last a few days.

Since the nature of festivals and fairs is temporary and the vendorsparticipating in these events are generally small local vendors who havelimited to no technology at their disposal; consumer informationgathering at such events is not possible.

Radio-frequency identification (RFID) is the wireless non-contact use ofradio-frequency electromagnetic fields to transfer data for the purposesof automatically identifying and tracking tags attached to objects. Thetags contain electronically stored information. Some RFID tags arepowered by and read at short ranges (a few centimeters) viaelectromagnetic induction. Other types of RFID tags may use a localpower source such as a battery, or else have no battery but collectenergy from the interrogating electromagnetic field, and then act as apassive transponder to emit microwaves or UHF (ultra high frequency)radio waves. Unlike a bar code, the RFID tag does not necessarily needto be within line of sight of the reader, and may be embedded in anobject.

RFID tags can be passive or active or battery-assisted passive. Apassive tag is cheaper and smaller because it has no battery. An activetag has an on-board battery and periodically transmits its ID signal. Abattery-assisted passive (BAP) tag has a small battery on board and isactivated when in the presence of an RFID reader.

RFID tags may either be read-only, having a factory-assigned serialnumber that is used as a key into a database, or may be read/write,where object-specific data can be written into the RFID tag by thesystem. Field programmable RFID tags may be write-once, read-multiple;“blank” RFID tags may be written with an electronic product code by theuser.

Generally fixed RFID readers are set up to create a specificinterrogation zone which can be tightly controlled. This allows a highlydefined reading area for when tags go in and out of the interrogationzone. Mobile RFID readers may be hand-held or mounted on carts orvehicles. But all of the aforementioned prior art methods are manual andrequire a work force to scan the RFID tags.

Despite advances in technology, prior art methods still have severalshortcomings e.g. a lack of information gathering about consumersampling at a festival or fair. Since the duration of a festival or fairis so brief, conventional methods for setting up and collecting consumerbehaviour information are not suitable or may cost too much to provide ameaningful business benefit. Thus consumer information is neithercollected nor compiled in real time to be useful due to the brevity ofthe event. Thus a wholesale change is needed in the way brands and/orvendors and/or manufacturers (distributors, event organizers,exhibitors, etc.) engage with their audience from basic entry all theway to post event communication and data mining.

To compound this problem, consumers have steadily been moving away fromcash based transactions as they don't want the hassle of carrying cashand coins, which can also be easily lost or stolen in the rush of afestival. One method to overcome this limitation is to use touchless andcashless transaction methods that provide convenience and save time. Onemethod of achieving touchless and cashless transactions is throughcredit cards. Wristbands have also arisen that are embedded with RFID(Radio-frequency identification) tags and can be used as a touchlesspayment fob. RFID tags allow for a “tap and go” style of payment becausethe information is transmitted wirelessly. Two-way radiotransmitter-receivers called readers send a signal to the tag and readits response. In such a transaction the user is not required to sign apiece of paper or to enter the PIN number, and neither there is anyverification of signature.

Prior art methods, such as paper tickets, used at fairs, festivals, andsimilar events to process visitors are manual and slow. Token systemsusing physical items to act as a medium for exchange for goods at theevent have been used but require the exchange of real currency foranother physical item that must be carried around. These do not improvethe guests' experience and often hinder that experience by now requiringplastic tokens or another medium to be cared for. Further, such tokensdo not allow for an automated way to capture the transaction data fromthe event. Tokens must be exchanged in a similar way as hard currencyand thus are equally slow and “dumb”.

Such methods are outdated and take away from the pleasure of attendingevents that are brief in nature.

SUMMARY

The present invention broadly relates to a system and method of venuecontrol using near field communications (NFC and RFID) Portals to managethe entrances and exits of temporary venues where visitors have beenissued temporary RFID tags for admittance. The system and method alsocontemplates the use of these RFID Portals for gathering visitorbehaviour information. The present invention provides a system andmethod of electronic touchless visitor processing for events that aretemporary, short term and transient in nature (for example a wine andcheese festival held over a long weekend). Other embodiments may beadapted for permanent locations.

According to a first aspect of the invention, an RFID portal is providedfor placing at an access point associated with a temporary event. Theaccess point is controlled by a security control. The portal has aportal body erectable on at least one side of a user pathway at theaccess point; and an RFID reader in the portal body for reading an RFIDtag issued to, and worn by, an individual user for the event that has anencoded unique UserID readable by the RFID reader. The RFID reader islocated in the portal body, so as to be physically proximate to alocation of the user's body where the RFID tag is worn. The RFID readeris in communication with a server which has stored a list of validUserIDs for the event. The RFID portal also has an indicator system forreceiving notification from the server that the read UserID is a validUserID for the event and generating an indication to the securitycontrol, such that the security control permits the user to proceedalong the pathway.

For example, where the RFID tag is in a bracelet or wristband format,the RFID reader may be positioned proximate to natural wrist height ofthe user walking by. Or, where the RFID tag is in an anklet orshoe-mounted format, the RFID reader may be positioned proximate to theuser's foot or ankle height. It is a goal of the invention to make theadmission process as low-impact as possible. The process of verificationof the user's “ticket” is done entirely through the RFID tag issued tothe user. The user does not need to stand in place and present this to asecurity guard or event personnel for scanning with a scan gun, but theuser simply walks very naturally through the portal area with the tagbeing scanned on the fly.

In some embodiments the security control may be a security guard. Inthis case, the indicator system may include a light that visiblydisplays the indication to the security guard (e.g. green for go; redfor stop). Alternatively, or in addition, the indicator system mayinclude an emitter that audibly provides the indication to the securityguard. In some embodiments, the security control is an automaticallyreleased barrier, gate, arm or turnstile, which is released with theindication.

Preferably, the RFID reader is capable of reading an ICODE SL12 16693tag or an ICODE SL12 15693 tag.

The RFID portal may further include a portal head mounted on the portalbody, which has: a first screen mounted generally away from the user;and a second screen mounted generally toward the user. The UserID may beassociated with other data stored on the server. At least some of thisother data may be retrieved and displayed on the first and/or secondscreen when the RFID tag is read. One or more messages related to theother data may also be displayed on the first and/or second screen whenthe RFID tag is read. For example, the other data may include: an age ordate of birth credential, an access or privilege credential, and astored funds balance.

For example, the first screen may display an access permitted decision,while the second screen displays a welcome message. The welcome messagemay be personalized to the user (e.g. indicating the user's name, or anid number, or particulars of the user's account, such as VIP status, orbuying credits or account balance).

In some embodiments, the RFID portal may be gangable with other RFIDportals at the access point, such that the user passes between twoadjacent RFID portals.

The access point may be an entry point to the event, or may for example,be an entry point to a subzone within the event.

Preferably, the RFID reader is further programmed for sending atimestamp of the user's entry to the server.

The RFID portal may also optionally include an RFID writer for writingdata or updated data to the RFID tag (e.g. adding or changing a fundsbalance associated with the RFID tag, or cancelling a single-use entrycredential, so that the user cannot re-enter the event).

According to a second aspect of the invention, a self-contained RFIDportal is provided for placing at an access point associated with atemporary event. The access point is controlled by a security control.The portal has a portal body erectable on at least one side of a userpathway at the access point; and an RFID reader in the portal body forreading an RFID tag issued to, and worn by, an individual user for theevent that has an encoded unique UserID readable by the RFID reader. TheRFID reader is located in the portal body, so as to be physicallyproximate to a location of the user's body where the RFID tag is worn. Aprocessor and storage is contained within the portal body. The storageincludes a locally-stored list of valid UserIDs for the event. Theprocessor is programmed for comparing the read UserID to the list ofvalid UserIDs for the event. An indicator system indicates a match fromthe comparing step to the security control, such that the securitycontrol permits the user to proceed along the pathway.

In one embodiment each visitor is given an RFID tag that may be embeddedin a wearable item e.g. a wristband or a necklace at the start of theevent. Each RFID tag has a unique UserID. In one embodiment each RFIDtag has a unique UserID. Optionally the RFID tag may allow funds to bepreloaded to it for later use at the venue. A visitor may also be ableto add a balance in advance to attending the event e.g. at the time ofregistration a consumer may opt to add $100 that can then be used viathe RFID tag to sample or purchase different products being show casedat the event. Thus when the visitor arrives at the fair or festival andis given the RFID wristband it includes a privilege to spend $100 at thedifferent sales booths setup at the venue.

A connected server stores the unique UserIDs of RFID tags for consumers.The connected server is preferably accessible over a network e.g. a LANor a WAN or over the internet.

The venue is equipped with one or more RFID Portals, such as at theentrance and exit of the venue. Each RFID Portal has an RFID readerembedded in it. Signaling between the RFID reader and the RFID tag canbe done in several different ways, depending on the frequency band usedby the RFID tag.

The one or more RFID Portals are in communication with a connectedserver that stores the UserIDs of the RFID tags. The connected servermay also optionally store any associated balances, age information, zonerestriction/privileges information etc. The connected server isaccessible over a network for example a local area network (LAN).

The RFID Portal may have two main sections the RFID Portal Head and theRFID Portal Body. The RFID Portal Head preferably has two displayscreens embedded at the opposite ends, e.g. LCD screens. Of the twodisplay screens, the first screen Screen1 is used for displayinginformation to the visitor and the second screen Screen2 is used fordisplaying the information to the security personnel.

The RFID reader embedded in the Portal Body is used for reading the RFIDtags worn by the visitors for controlling the access to the venue.

The RFID Portal may also incorporate one or more indicator LED lightse.g. LED lights that are used for communicating certain statusinformation with the visitors and the security personnel. The RFIDPortal in addition may also use other sensory methods e.g. auditorybeeps may also be used for conveying some or part of the information tothe security personnel.

The RFID Portal can be self-contained with the RFID reader, electronicsfor communicating with the connected server and the Portal Head with thetwo display screens.

Through the RFID technology festival goers are able to engage with thevendors during and after the event. The RFID Portals provide aconvenient and fast visitor processing system enabling visitors to spendmore time enjoying the festivities and less time waiting in lines.

The venue of a fair or a festival may be set up with one or more RFIDPortals that embed RFID readers, a connected server that stores theUserIDs of the RFID tags, associated balances, age information, zonerestriction/privileges information. The server is preferably accessibleby the RFID Portals over a network for example a local area network(LAN).

Preferably, the RFID tags are embedded in some kind of a wearableformat, e.g. a wristband, an ankle-band, a shoe-mounted format, a pairof sunglasses, a necklace, a badge, etc. Each RFID tag has a uniqueUserID associated with it.

Preferably, the system also allows for the collection and compilation ofdata using the RFID Portals. The information is gathered in real time tobe useful via the RFID tags worn by visitors either in a wristband orother RFID wearable item. This entrance/exit data may also be combinedwith other user data collected through the RFID tags (e.g. through othertransactional or sampling readers located throughout the venue), orthrough data provided by the user before or after the event.

Unique IDs may also be issued to each of the vendors (VendorID)participating in the event, while also providing ProductIDs for each ofthe products that the vendor may be offering for sampling at the event.

Real time information can then be gathered using RFID Portals, at anevent level or subzone (e.g. booth). Each time a consumer enters abooth, samples or purchases one or more products and then leaves thebooth, information may be gathered as to when consumer entered a booth,what products were sampled or purchased in what order they were sampledor purchased, and when the consumer left the booth.

For example when the consumer visits a booth e.g. a wine tasting toothof a winery at a wine and cheese festival that is being held over aweekend the RFID wristband UserID may be captured and saved to theserver; while VendorID is saved to the RFID wristband of the consumer.The ProductIDs of the products sampled and purchased by the saidconsumer at this booth are also captured and saved to the RFID wristbandand the server. When the consumer leaves the wine tasting booth RFIDwristband UserID is captured and saved to the server; while VendorID issaved to the RFID wristband of the consumer.

Similarly when the said consumer visits a second and a third booth theRFID UserID and timestamps are captured at arrival and departure of theconsumer to these booths; and the ProductIDs of the products sampled andpurchased at the second and third booth are also captured and saved tothe RFID wristband and the server.

The ProductIDs may be saved to the server or the RFID wristband of theconsumer. In an alternate embodiment the ProductIDs and the VendorID aresaved both to the server and the RFID wristband of the consumer.

In one embodiment gathered information may be compiled about consumer'svisits to different booths during an event and about the productspurchased or sampled at each of the booths visited by the consumer. Thisinformation may be shared with a vendor (e.g. how many consumers visitedthe vendor's booth and what products were purchased and sampled).Similarly information may be shared with individual consumers abouttheir visit to different booths and which products were purchased andsampled during the visit.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flow diagram of a basic flow for an RFID portal enabledevent.

FIG. 2 is a first side (user-facing) view of an RFID portal.

FIG. 3 is a second side (security-facing) view of an RFID portal.

FIG. 4 is a flow diagram of a sample processing flow for RFID portal.

FIG. 5 is a flow diagram of credential verification (here, in an agerestricted zone).

FIG. 6 is a flow diagram of data compilation using a system of RFIDportals.

DETAILED DESCRIPTION

Before embodiments of the invention are explained in detail, it is to beunderstood that the invention is not limited in its application to thedetails of the examples set forth in the following descriptions orillustrated drawings. The invention is capable of other embodiments andof being practiced or carried out for a variety of applications and invarious ways. Also, it is to be understood that the phraseology andterminology used herein is for the purpose of description and should notbe regarded as limiting.

Before embodiments of the software modules or flow charts are describedin detail, it should be noted that the invention is not limited to anyparticular software language described or implied in the figures andthat a variety of alternative software languages may be used forimplementation of the invention.

It should also be understood that many components and items areillustrated and described as if they were hardware elements, as iscommon practice within the art. However, one of ordinary skill in theart, and based on a reading of this detailed description, wouldunderstand that, in at least one embodiment, the components comprised inthe method and tool are actually implemented in software.

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer usableprogram code embodied in the medium. In order to provide a context forthe various aspects of the disclosed invention, as well as the followingdiscussion are intended to provide a brief, general description of asuitable environment in which the various aspects of the disclosedinvention may be implemented. While the invention has been described inthe general context of computer-executable instructions of a programthat runs on one or more computers, those skilled in the art willrecognize that the invention also may be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types. Moreover, it willbe appreciated that the present system and method may be practiced withother computer system configurations, including single-processor,multiprocessor or multi-core processor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., personal digital assistant (PDA), phone, watchor other electronic gadgets incorporating the capacity to compute),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects may also be practiced indistributed computing environments where tasks/routines/processes etc.are performed by remote processing devices that are linked through acommunications network e.g. a local area network (LAN) or the Internet.However, some, if not all aspects of the invention may be practiced onstand-alone computer(s). In a distributed computing environment, programmodules may be located in both local and remote memory storage devices.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. Computer code may also be written in dynamic programminglanguages that describe a class of high-level programming languages thatexecute at runtime many common behaviours that other programminglanguages might perform during compilation. JavaScript, PHP, Perl,Python and Ruby are examples of dynamic languages. Additionally computercode may also be written using a web programming stack of software,which may mainly be comprised of open source software, usuallycontaining an operating system, Web server, database server, andprogramming language. Some embodiments may use well-known open-sourceWeb development platforms using Linux, Apache, MySQL and PHP. Otherexamples of environments and frameworks using which computer code mayalso be generated are Ruby on Rails which is based on the Rubyprogramming language, or node.js which is an event-driven server-sideJavaScript environment. In the present case, the code is specialized toexecute functions described herein which enable a smoother and moreefficient technological process.

Computing devices e.g. terminals or readers that enable a user to engagewith the invention in general may include a memory for storing a controlprogram and data, and a processor (CPU) for executing the controlprogram and for managing the data, which includes user data resident inthe memory and includes buffered content. The computing device may becoupled to a video display such as a television, monitor, or other typeof visual display while other devices may have it incorporated in them(iPad, iPhone etc.). An application or an app or other simulation may bestored on a storage media such as a USB memory key, flash memory, orother type of memory media all collectively referred to as “removablemedia” in this disclosure. The app may also be downloaded from theinternet. The removable media can be inserted to the console of acomputing device where it is read. The console can then read programinstructions stored on the removable media and present a user interfaceto the user. The user interface may preferably be a graphical userinterface (GUI).

FIG. 1 shows a preferred embodiment of the basic flow of the invention100. A system and method is provided using RFID Portals for venuecontrol and automatic processing of visitor admittance 101.

The present invention relates to a system and method of electronictouchless visitor processing for events that are temporary, short termand transient in nature. With or without adaptation, the system may alsobe suitable for permanent venues.

Some embodiments of related systems have been described in theapplicant's copending U.S. patent application Ser. No. 14/717,234 (filedMay 20, 2015); Ser. No. 14/946,287 (filed Nov. 19, 2015); and Ser. No.15/048,551 (filed Feb. 19, 2016), the disclosures of which areincorporated herein by reference.

One or more visitors may attend an event 102, for example a wine andcheese festival held over a long weekend.

Each visitor is given an RFID tag at the start of the event 103. TheRFID tag may be embedded in a wearable item e.g. a wristband, anklet ora necklace.

Each RFID tag has a unique UserID 104. Optionally the RFID tag may allowfor funds to be loaded to it for later use at the venue. A visitor mayalso be able to add a balance in advance to attending the event e.g. atthe time of registration a consumer may opt to add $100 that can then beused via the RFID tag to sample or purchase different products beingshowcased at the event. Thus when the visitor arrives at the fair orfestival and is given the RFID wristband it includes a privilege tospend $100 at the different sales booths setup at the venue.

A connected server stores the unique UserIDs of RFID tags for consumers105. The connected server is preferably accessible over a network e.g. aLAN or a WAN or over the internet.

The venue is preferably equipped with one or more RFID Portals 106, suchas at the entrance and exit of a venue. Each RFID Portal has an RFIDreader embedded in it. Signaling between the RFID reader and the RFIDtag can be done in several different ways, depending on the frequencyband used by the RFID tag. Optionally, the RFID Portal also includes awriter (not shown) that allows data to be written (or rewritten) to thetag.

The one or more RFID Portals are in communication with a connectedserver that stores the UserIDs of the RFID tags. The connected servermay also optionally store any associated balances, age information, zonerestriction/privileges information etc. The connected server isaccessible over a network for example a local area network (LAN).

The unique UserIDs of RFID tags may be stored on the server in variousformats and configurations. In the preferred embodiment the list ofunique UserIDs of RFID tags may be available in a CSV (Comma SeparatedValues) format from the supplier. This CSV file is then uploaded to theserver. The system then automatically initializes the RFID tags bycreating a unique encryption method for that specific tag and writes theoffline information to the memory of the RFID tag when the RFID tag isfirst read by an RFID reader in the system. In an alternativeembodiment, the function of the server is replaced by a self-containedsystem in the RFID portal, which includes at least a processor and localstorage containing the list of valid UserIDs.

In one embodiment of the invention the system may use standardized RFIDtags (ICODE SLI2 15693 on 13.56 MHz (HF)), the most common tag type forinventory tracking.

RFID tags contain at least two parts: an integrated circuit for storingand processing information, modulating and demodulating aradio-frequency (RF) signal, collecting DC power from the incidentreader signal, and other specialized functions; and an antenna forreceiving and transmitting the signal. The tag information is stored ina non-volatile memory. The RFID tag includes either a chip-wired logicor a programmed or programmable data processor for processing thetransmission and sensor data, respectively.

Such RFID tags have a memory which has two sectors: the ROM (read onlymemory) and the R/W (read/write) memory. The ROM stores the UserID (alsoknown as UID) of the RFID tag. This information is burnt to the ROM atthe time of manufacturing and cannot be changed later. The second sectorof the memory is a R/W memory, where transactional information is storede.g. information such as balance, one or more previous transactions,zone restrictions, age limit, etc. Such information may be preferablystored in an encrypted format. The preceding list of items stored on theRFID tag is exemplary and the invention is not limited to theseexamples.

An RFID reader transmits an encoded radio signal to interrogate the RFIDtag. The RFID tag receives the message and then responds with itsidentification and other information. This may be only a unique tagserial number, or may include product-related information such as astock number, lot or batch number, production date, or other specificinformation. In case of the double tap payment method, the balance iswritten to the RFID tag in addition to some other information likebalance, age limit and zone restrictions etc.

When written into the RFID tag by an RFID printer, the tag contains a96-bit string of data. The first eight bits are a header whichidentifies the version of the protocol. The next 28 bits identify theorganization that manages the data for this tag; the organization numberis assigned by the EPCGlobal consortium. The next 24 bits are an objectclass, identifying the kind of product; the last 36 bits are a uniqueserial number for a particular tag. These last two fields are set by theorganization that issued the RFID tag. Similar to a URL, the totalelectronic product code number can be used as a key into a globaldatabase to uniquely identify a particular product.

Generally, the read range of an RFID tag is limited to the distance fromthe reader over which the tag can draw enough energy from the RFIDreader field to power the tag. RFID tags may be read at longer rangesthan they are designed for by increasing reader power.

In one embodiment the use of RFID Portals prevents visitors fromfraudulently entering any areas that are restricted.

FIG. 2 shows a preferred embodiment of the RFID Portal 200. The RFIDPortal has two main sections the RFID Portal Head 201 and the RFIDPortal Body 202.

In the preferred embodiment the RFID Portal Head 201 preferably has twodisplay screens embedded at the opposite ends. Each RFID Portalincorporates two or more display screens e.g. LCD screens. Of the twodisplay screens, the first screen Screen1 203 is used for displayinginformation to the visitor and the second screen Screen2 204 is used fordisplaying the information to the security personnel.

In the preferred embodiment the RFID Portal Body 202 has an RFID Reader205 embedded in it. The RFID reader is used for reading the RFID tagsworn by the visitors for controlling the access to the venue. The RFIDreader is preferably located at a height so as to be near where the tagis worn on the user's body. In the example shown, the RFID tag might becontained in a wristband or bracelet, and the RFID reader is preferablyat approximately natural wrist height for an average visitor. Because ofthis positioning of the RFID reader, the user/visitor does not need toadopt any specific physical position for the tag to be read (e.g. raisearm to “show” the tag to a security personnel or scanning gun), but cansimply walk through the portal naturally.

Each RFID Portal incorporates an RFID reader. Signaling between the RFIDReader 205 and the RFID tag can be done in several different ways,depending on the frequency band used by the RFID tag. RFID tagsoperating on LF (Low Frequency) and HF (High Frequency) bands are, interms of radio wavelength, very close to the reader antenna because theyare only a small percentage of a wavelength away. An RFID tag iselectrically coupled with the transmitter in the reader. The RFID tagcan modulate the field produced by the reader by changing the electricalloading the tag represents. By switching between lower and higherrelative loads, the RFID tag produces a change that the RFID reader candetect. At UHF (Ultra High Frequency) and higher frequencies, the RFIDtag is more than one radio wavelength away from the reader, requiring adifferent approach.

The RFID Portal may also incorporate one or more indicator LED lightse.g. LED light 206 that is used for communicating certain statusinformation with the visitors. The RFID Portal in addition may alsopreferably use other sensory methods e.g. auditory beeps may also beused for conveying some or part of the information to the visitors andthe security personnel.

The RFID Portal can be self-contained with the RFID reader, electronicsfor communicating with the connected server and the Portal Head with thetwo displays screens. Further, the UserIDs can be locally stored in theRFID Portal and compared locally using an onboard processor. Otherfunctions may also be programmed locally and other kinds of data storedlocally (e.g. timestamp collection of user visits).

In one embodiment the RFID Portals control the entrance and the exit toa given venue by allowing entrance or denying entrance based on thevalidity of the RFID tags embedded in wearable items like a wristband.

FIG. 3 shows a second embodiment (or at least a separate perspective) ofthe RFID portal 300. The RFID Portal has two main sections the RFIDPortal Head 201 and the RFID Portal Body 202. In the preferredembodiment the RFID Portal Head 201 preferably has two display screensembedded at the opposite ends. Each RFID Portal incorporates two or moredisplay screens e.g. LCD screens. Of the two display screens, the firstscreen Screen1 203 is used for displaying information to the visitor andthe second screen Screen2 204 is used for displaying the information tothe security personnel.

An indicator LED light 207 may be used for communicating certain statusinformation with the security personnel. Other embodiments may employLED lights and other sensory methods for conveying information to thesecurity personnel e.g. auditory beeps may also be used for conveyingsome or part of the information to the security personnel e.g. two shortbeeps could be used for valid access while a longer louder beep may beused for an invalid access. The auditory beeps may also preferably beaccompanied with LEDs e.g. lighting one or more green LEDs implies avalid access while lighting one or more flashing red LEDs implies aninvalid access.

FIG. 4 shows one embodiment of the process 400. The visitor taps theRFID tag on the RFID Portal or simply walks past the RFID Portal suchthat the RFID tag is read by the reader 401.

In popular events, at peak times, lines can be long, and having to showa card or other access control credential takes time. In the presentsystem, by allowing the user to just walk past the RFID Portal, the RFIDtag in the wearable item can be automatically read and the informationdisplayed to the consumer and the security personnel in two differentand separate screens. As the verification of the UserID is donesubstantially in real time, the user's progress (and progress of theline through the entrance) is not impeded.

The RFID Portal reads the RFID tag 402.

The system checks the validity of the RFID tag 403. The validity of theRFID tag can be checked by reading its UserID and passing this UserID tothe server for validation. The server may preferably have a database ora list of all valid UserIDs for the RFIDs that are related to an event,the associated balances, a list of recent transactions, age and zonerestrictions if any amongst other information about the bearer of theRFID tag.

The system checks whether the RFID tag valid 404. If the UserID of theRFID tag is not valid 404 a then the user/visitor is disallowed fromentering the venue. A notification may be displayed on RFID PortalScreen1 for the visitor as the visitor is disallowed from entering thevenue 405. Preferably information is also displayed for the visitornoting the reason that they are not allowed to enter e.g. access isdenied due to an expired ticket, or due to an age restriction.

The system may also display a notification on RFID Portal Screen2 forthe security personnel 406. In certain embodiments a security person mayalso be manning the entrance or exit of a venue. In other embodimentsthe RFID Portal may be fully automated (e.g. with a turnstile gate)allowing or disallowing entrance to the venue.

If the UserID of the RFID tag is valid 404 b, then the system allows thevisitor to enter the venue. Thus only if the UserID of the RFID tagmatches with a valid UserID in the list/database on the server then itis considered that the RFID tag is valid. Alternatively, in someembodiments, rather than a “white list” (valid UserIDs) approach, a“black list” approach may be used (i.e. checking for specific bannedpersons instead).

On verification, a message may be displayed on the RFID Portal Screen1welcoming the visitor 407. Further, a message may be displayed for thesecurity personnel on RFID Portal Screen2 408. At this point, thevisitor may be allowed to enter the venue 409. Further informationrelevant to the visitor may also be provided 410.

FIG. 5 shows one embodiment of the process flow, specific to ageverification 500. The system preferably checks the age limit whengranting access to an age restricted area that requires an age limit(e.g. an alcoholic beverage) 501. Certain events e.g. a festival may bedivided into one or more zones. The different zones in a festival may berequired in order to segregate the visitors based on their age or theirpayment levels. For example a fair may have an area where alcoholicbeverages can be sampled or purchased, that is only accessible topersons aged 19 or over and any products/services being vended in thiszone may only be sampled/purchased by these people.

For example an event like a fair may have products or services for saleor sampling that are age restricted e.g. alcohol or products aimed at anadult audience. Thus it is important to check the age of a visitor tosuch an area to ensure that age restricted products and services areonly offered to the legal audience.

The system checks whether the visitor is over the age limit, e.g. 19years 502. The RFID Portal reads the RFID UserID and communicates theRFID UserID with the connected server.

The server may store this information so that when an RFID tag is readby an RFID Portal it can verify the age restrictions, zonerestrictions/privileges by connecting to the server and querying theUserID of the RFID tag and checking its bearer's restrictions/privilegesbefore allowing the visitor to enter such an area. Alternatively theRFID tag may preferably contain this information that defines thezone(s) where the RFID tag is valid.

If the age of the person associated with the UserID is not valid for theage restricted area 502 a the system preferably displays a notificationon RFID Portal Screen1 and disallows the visitor from entering the agerestricted venue 503.

The system also preferably displays a notification on the RFID PortalScreen2 for the security personnel 504.

If the owner of the RFID UserID is valid for the age restricted area 502b a message may be displayed on the RFID Portal Screen1 welcoming thevisitor 505.

A message may also be displayed for the security personnel on RFIDPortal Screen2 506 preferably indicating that the visitor is ofappropriate age. The system allows the visitor to enter the agerestricted area 507 e.g.

Further information may be provided to the visitor that may be relevant508, and a sales person may be allowed to vend age-restricted productsto the visitor.

The server may preferably store the age or date of birth informationabout the consumer, so that when an RFID tag is read by the RFID Portalthe age can be verified before allowing a visitor to enter the agerestricted area.

In another embodiment the RFID tag may preferably contain the age ordate of birth information about the visitor. Alternatively the RFID tagand the server both may store the age and date of birth informationabout the visitor.

FIG. 6 shows one embodiment of the flow, related to data compilation600. Real time information is preferably gathered from one or more RFIDPortals in communication with a connected server 601. The RFID Portalsmay be strategically placed in different areas of a venue and read theRFID tags worn by the visitors. For example the RFID Portals may readthe RFID tag of a visitor each time said visitor enters an area orbooth, samples or purchases one or more products and then leaves thebooth. Information may be gathered as to when a particular visitorentered an area or booth, what products were sampled or purchased inwhat order they were sampled or purchased, and when did the visitorleave the booth. This may be done using the portals themselves, or theportals may be part of a broader network of RFID readers/terminalsthroughout an event area/venue.

Preferably, the RFID Portal captures the visitor RFID UserID andtimestamp at entry and then at the exit of a vendor booth. The capturedvisitor RFID UserID and timestamp are saved to the server or the RFIDtag or both. In one embodiment this information may be first saved tothe RFID tag in realtime, but may be uploaded to the serverasynchronously. In an alternate embodiment this information is saved toboth the RFID tag and the connected server in realtime.

The system may compile information about visitor movement in the venue602. For example a consumer visits a wine and cheese festival and duringthe visit goes to a cheese outlet booth, then goes to the winery boothand then goes to the beer booth.

The system may compile information about areas/booths visited by thevisitor 603.

For example at a wine and cheese festival, a consumer visits a cheeseoutlet booth and tries a cream cheese and an aged cheddar cheese; thengoes to a winery booth and tries a red wine and a white wine; andsubsequently at lunch visits the beer booth and samples different typesof beers. A full timestamped log of an individual consumer's activityduring a festival may be gathered.

The gathered information may then be compiled 604.

This compiled information may be shared with the venue organizer and oneor more vendors in several ways. For example, basic history or log datafor the user may displayed on Screen2 of the RFID Portal 605.

The information about all visitors who visited the booth of a particularvendor may include but is not limited to the following:

-   -   What was the peak time at the booth in terms of traffic    -   What was the slow time at the booth in terms of traffic    -   When most sales were conducted    -   When least sales were conducted    -   Average time consumers spent in the area or booth (by capturing        entry time and departure time)    -   Average visitor spending at the vendor    -   In what sequence visitors visited (which area/booth was visited        first, which area/booth was visited last etc.)    -   Which products were sampled most    -   Which products were purchased most    -   Which products were sampled least    -   Which products were purchased least

The information about a particular visitor who visited the booth of aparticular vendor may include but is not limited to the following:

-   -   When did the visitor visit the area/booth    -   Was the visit during peak time or during slow time    -   How much time did this visitor spend and how it compares to the        average time for all visitors who visited this area/booth    -   How much did this visitor spend and how it compares with the        average visitor spending at this vendor    -   In what sequence did this visitor visit the vendor area/booth    -   Which products were sampled    -   Which products were purchased    -   Ratio of sampled products to purchased products

Alternatively compiled information may also be sent to the vendor via anattached file in an e-mail, mailing printed results, a link to thecompiled information that is accessible over the internet, and otherelectronic methods conducive to sharing and sending information over theinternet, e.g. after the event is over or at the end of the day for amulti-day event or at given intervals during an event.

Optionally part or complete compiled information may be shared with thevisitor. This may be displayed for example on Screen1 of the RFID Portal606.

Alternatively this information may be shared with the visitor after thevisit is complete e.g. via an attached file in an e-mail, mailingprinted results, a link to the compiled information that is accessibleover the internet, and other electronic methods conducive to sharing andsending information over the internet.

In one embodiment the information about a particular visitor who visitedthe event e.g. the festival or fair may include but is not limited tothe following:

-   -   How many booths did the visitor visit    -   In what order did the visitor visit the area/booths    -   Time spent at each of the area/booths    -   Which products were sampled and or purchased at each area/booth        visited    -   How much did the visitor spend in total at the event    -   How much did the visitor spend at each area/booth    -   What products were purchased/sampled by the visitor    -   What products were most popular at the event    -   In what sequence products were sampled at a given area/booth    -   Comparison of visitor time spent at the area/booth with the        average time of all visitors at the same booth    -   Comparison of visitor spending at the area/booth with the        average spending of all visitors at the same booth

In one embodiment the RFID Portal captures the RFID tag UserID andtimestamp at arrival and departure of the visitor to a given vendorbooth.

In the preferred embodiment the RFID tag UserID and the VendorID may becaptured and stored on the server at the time of entry and at the timeof departure. In other alternate embodiments other combinations ofVendorIDs and RFID UserIDs may be read at the RFID Portal as the visitorwalks past it, and is stored on the RFID tag, the connected server, thesales terminal, the top-up terminal or other such storage device ormechanism.

Thus by tracking the RFID tag UserID of a particular visitor over aperiod of time when attending a fair or a festival, along with theVendorIDs of the booths visited and the ProductIDs of the productspurchased or sampled a complete visitor profile can be assembled thatreflects the visitor's purchasing and sampling preferences during thatvisit.

The above are exemplary and not limiting, in fact the intent is to coverall such information that may be relevant and gathered at an event andshared with the vendors or consumers attending the event.

In one embodiment of the invention the RFID tags are customized beforeusage. In an alternate embodiment of the invention the system and methodof the invention may use generic RFID tag for example RFID tags havingan ICODE SLI2 15693.

One embodiment of the invention may use Active Reader Passive Tag (ARPT)system that has an active reader, which transmits interrogator signalsand also receives authentication replies from passive RFID tags.

These descriptions exemplify only some of the several possibleembodiments of the invention and are not meant to be exhaustive. Theintent is to cover all practical possibilities and combinations.

It should be understood that although the term application has been usedas an example in this disclosure but in essence the term may also implyto any other piece of software code where the embodiments of theinvention are incorporated. The software application can be implementedin a standalone configuration or in combination with other softwareprograms and is not limited to any particular operating system orprogramming paradigm described here.

The computer program comprises: a computer usable medium having computerusable program code, the computer usable program code comprises:computer usable program code for presenting graphically to the usersoptions for scrolling via the touch-screen interface.

The examples noted here are only for illustrative purposes and there maybe further implementation embodiments possible with a different set ofcomponents. While several embodiments are described, there is no intentto limit the disclosure to the embodiment or embodiments disclosedherein.

All aspects are illustrative and not restrictive and may be embodied inother forms without departing from their spirit and essentialcharacteristics.

What is claimed is: 1-21. (canceled)
 22. A method of processing anaccess transaction, comprising: issuing ticketing particulars to aplurality of users for an event; associating each set of ticketingparticulars with an RFID or NFC tag having a unique UserID; providing aportal body having a first upright portion on one side of an accesspathway and a second upright portion on an opposing side of the accesspathway; and providing a programmed functionality at the portal body forreading an RFID or NFC signal at 13.56 MHz frequency, such that: a tagthat is worn or hand-held by a user is read merely by the user passingbetween the first and second upright portions of the portal; the UserIDof the tag is communicated to a server which has stored a list of validUserIDs for the event; and upon receiving notification from the serverthat the read UserID is a valid UserID for the event, an indication isgenerated on an indicator system of the portal which signals a securitycontrol to permit the user to proceed along the pathway beyond thesecurity control.
 23. The method of claim 22, wherein the securitycontrol is an automatically released barrier, gate, arm or turnstile.24. The method of claim 22, wherein the programmed functionality is in adevice, and the device is a phone mounted on or near the portal body.25. The method of claim 22, wherein the tag is in a phone.
 26. Themethod of claim 22, wherein the indicator system includes a light. 27.The method of claim 22, wherein the indicator system includes anemitter.
 28. The method of claim 22, wherein the indicator system is ina portal head mounted on an upper portion of the portal body, having atleast one screen.
 29. The method of claim 22, wherein the UserID isassociated with other data stored on the server.
 30. The method of claim29, wherein at least some of the other data is retrieved and displayedon the at least one screen when the tag is read.
 31. The method of claim29, wherein a message related to the other data is displayed on the atleast one screen when the tag is read.
 32. The method of claim 29,wherein the other data includes at least one of: an age or date of birthcredential, an access or privilege credential, and a stored fundsbalance.
 33. The method of claim 29, wherein the other data includes alink to an account or profile of the user.
 34. The method of claim 28,wherein the at least one screen consists of a first screen facinggenerally away from the user, and a second screen facing generallytoward the user.
 35. The method of claim 34, wherein the first screendisplays an access permitted decision, and the second screen displays awelcome message.
 36. The method of claim 35, wherein the welcome messageis personalized to the user.
 37. The method of claim 28, wherein the atleast one screen displays an access denied message if the user does notpresent a tag having a UserID that is valid at the time it is read. 38.The method of claim 37, wherein the message includes a reason.
 39. Themethod of claim 22, further comprising sending a timestamp of the user'sentry to the server.
 40. The method of claim 39, wherein a plurality ofportal bodies are provided throughout an event venue, and the serverstores a continuous record of timestamps of a user's progress throughthe event venue.
 41. The method of claim 39, wherein the timestamps arestored together with timed records of purchases or other actions by theuser during the event.